System and method to search and verify borrower information using banking and investment account data and process to systematically share information with lenders and government sponsored agencies for underwriting and securitization phases of the lending cycle

ABSTRACT

Account data (e.g., balance information) for accounts at a plurality of financial institutions (or government agencies) is stored (and updated) in a central database system and accessed using a personal identifier, such as a social security number. Risk data may be generated for accounts based on the account data. The account data and risk data are accessed in response to either an account search request (e.g., from a government entity and relating to a benefits program or a subpoena) or an account verification request (e.g. from a mortgage company and relating to a mortgage application).

CROSS-REFERENCES TO RELATED APPLICATIONS

This patent application is a continuation-in-part of U.S. patent application Ser. No. 14/959,881 filed Dec. 4, 2015 and titled “System and Method for Locating and Accessing Account Data to Verify Income”, which is a continuation-in-part of U.S. patent application Ser. No. 13/213,975 filed Aug. 19, 2011 and titled “System and Method for Locating and Accessing Account Data”, which claims priority to U.S. Provisional Patent Application No. 61/499,599 entitled, “Systems and Methods for Fraud Detection/Prevention for a Benefits Program,” filed Jun. 21, 2011, the complete disclosures of which are hereby incorporated by reference herein for all purposes.

BACKGROUND OF THE INVENTION

Account balance and other information for accounts held by an account owner are often needed by third parties for various reasons. For example, when applying for a mortgage, an applicant is typically required to provide information on all of the applicant's accounts to ensure there is sufficient cash attributable to the applicant (e.g., to use as a down payment). As another example, when applying for government benefits, such as supplemental security income (SSI) or other cash or services programs, a beneficiary's accounts must be located to ensure available assets have not been illegally transferred or do not otherwise exceed any qualification amount limits.

Searching for and verifying account balances can be difficult and time consuming. For example, in the case of a mortgage application, where an applicant has a number of accounts at different banks or other institutions (as used herein, “institutions” may include any type of financial service organizations, such as banks, credit unions, third-party payment services such as PayPal or the like, online banking services, online virtual money account systems, investment firms, brokerages, credit card companies, loan companies, check cashing services, payday loan services, government institutions, or any other entity providing financial services or information), verifying account balances may involve sending written requests to a number of different institutions, and each institution conducting a manual look-up for each specified account. Further, the applicant may not have complete account numbers or may not remember or provide information on all accounts. Even if the applicant has account numbers, the applicant may not provide the correct bank name or ID (such as a routing and transit number) to enable convenient and timely verification. In other cases, when the applicant has all the necessary account information, and even if a current balance has been confirmed by a bank, that balance may not be legitimate. That is, an applicant may have received or borrowed funds from another person (such as a relative) to temporarily show an account balance larger than what is actually owned by the account holder, to fraudulently qualify for a mortgage, loan, or government benefit.

In the case of an application for government benefits, an applicant may not disclose accounts, or income reflected in those accounts that would result in disqualification under the benefits program, or may have made transfers out of accounts to conceal assets.

Further, government and law enforcement agencies may from time to time have need to execute and serve subpoenas or National Security Letters (“NSLs”) pursuant to 18 U.S.C. §2709 (or other applicable statutes) to institutions to gain access to financial accounts or information for individuals or entities (such as corporations) named in such subpoenas. However, it is time consuming and expensive for such government and law enforcement agencies to locate which institutions may have information regarding an individual or entity named in a subpoena, and the institutions waste significant resources and expense responding to such subpoenas especially when there is no account or financial information for the named individual or entity that is accessible by the particular institution. The problem is magnified by the current approach of law enforcement to take a “shotgun” approach by delivering subpoenas or NSLs to a large number of major institutions in an attempt to find any applicable accounts for a person or entity of investigatory interest.

Thus, there is a need for systems and methods to locate, verify and/or access account information, especially for accounts that are maintained across a number of different institutions.

BRIEF SUMMARY OF THE INVENTION

Embodiments of the present invention provide systems and methods for locating and accessing assets, such as accounts. For purposes of the present disclosure, accounts may include, but are not limited to, deposit accounts such as checking, savings, CDs, money market accounts in the United States, or International accounts. Accounts may also include (i) reward or loyalty accounts providing merchant reward points, such as in the exemplary case of retail sales; (ii) online financial accounts such as PayPal accounts; (iii) online gaming such as Farmville or Second Life; or (iv) frequent flyer programs or stored value accounts. Further, accounts may include credit or loan accounts, credit card accounts, debit accounts, prepaid accounts, or any account regarding any desired type of financial information.

According to one aspect, a system includes a database storing data for accounts from a plurality of institutions. The stored data for each respective account comprises at least a personal identifier for an account holder of that respective account. The system further includes a processor configured to receive a request to locate assets. The request includes a submitted personal identifier, and the processor is configured to automatically locate one or more accounts by matching the submitted personal identifier to a personal identifier stored in the database for the located accounts. The processor is further configured to retrieve from the database stored data associated with the located accounts, and to produce a report. The report indicates the assets contained in the one or more located accounts, and the report also indicates a pattern of deposits into at least one of the located accounts. The processor is further configured to provide the report to an entity from which the request to locate assets was received.

According to another aspect, a computer-implemented method comprises providing a database and storing, in the database, account data for accounts maintained at a plurality of institutions. The account data for each respective account comprises at least a personal identifier for an account holder of that respective account. The method further comprises receiving a request to locate assets, the request including a submitted personal identifier, and automatically locating one or more accounts by matching the submitted personal identifier to the personal identifier stored in the database for the located accounts. The method further comprises retrieving at least some of the account data for the located accounts, and producing a report. The report indicates the assets contained in the one or more located accounts, and the report also indicates a pattern of deposits into at least one of the located accounts. The method further comprises providing the report to an entity from which the request to locate assets was received.

According to another aspect, a system comprises a database storing data for accounts from a plurality of institutions. The stored data for each respective account comprises at least a personal identifier for an account holder of that respective account. The system further includes a processor configured to receive, from a first requesting entity, a request to locate assets. The request includes a submitted personal identifier, and the processor is configured to automatically locate one or more accounts by matching the submitted personal identifier to a personal identifier stored in the database for the located accounts. The processor is further configured to retrieve from the database stored data associated with the located accounts, to produce a report that indicates the assets contained in the one or more located accounts, and to provide the report to the first requesting entity. The processor is further configured to receive, from a second requesting entity at a time later than the production of the report, a request for information contained in the report, the request including an identifier of the report, and to provide information contained in the report to the second requesting entity.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system for locating and accessing account information in accordance with embodiments of the invention.

FIG. 2 illustrates exemplary data provided to and stored in the database system of FIG. 1.

FIG. 3-5 are flow diagrams illustrating several processes used within the database system of FIG. 1, for locating and accessing account data.

FIG. 6 is a block diagram of one suitable scoring model and process for use in one embodiment of the invention.

FIG. 7 is a flow diagram illustrating a process used within the database system of FIG. 1, in accordance with an alternative embodiment.

FIG. 8 is a block diagram of a computer system upon which various devices, systems, and processes described in conjunction with FIG. 1-7 may be implemented.

FIG. 9 illustrates relationships between various parties involved in a scenario in accordance with embodiments of the invention.

FIG. 10 is a flow diagram illustrating steps performed according to some embodiments of the invention.

FIG. 11 is a flow diagram illustrating steps performed by a location/verification service provider, according to embodiments of the invention.

DETAILED DESCRIPTION OF THE INVENTION

Described embodiments of the present invention provide means for enabling assets (such as financial accounts owned by an account holder) to be located and accessed, even when maintained at a number of different institutions. In some embodiments, accounts are located using a personal identifier associated with the account holder, rather than an account number. In one specific embodiment, the personal identifier is a social security number (SSN).

In certain described embodiments, a system for locating assets may receive two different types of requests to locate assets (such as financial accounts). One such request may be an asset search request, and the other may be an asset verification request.

Briefly, as examples, an asset search request might be used by a government entity to locate accounts of a person applying for welfare benefits or some other form of government assistance. Government programs providing benefits (particularly welfare benefits) often have criteria that permit applicants/beneficiaries to qualify only as long as their assets (such as checking, savings and other financial accounts) have balances below a specified threshold. As an example, in many states, a beneficiary must have no more than $2000 in assets in order to qualify for Medicaid nursing home benefits. The systems and methods described herein permit an asset search for any accounts held by the beneficiary in order to confirm that balances in accounts held by the beneficiary are in fact below the required threshold. In other embodiments, transaction data in an identified account may be evaluated to determine or verify benefits eligibility. For example, where benefits eligibility is based on or related to income, a system and method could additionally provide account data relevant to the risk that a beneficiary is receiving income (e.g., deposited into an account) that would make the beneficiary ineligible for benefits. As a more specific example, in the case of unemployment insurance benefits paid by a government agency, transaction data in an identified account could be evaluated to provide risk scores and/or indicators pertaining to whether there might be employment income deposited to an account that would make the account holder ineligible for receiving or continuing to receive unemployment benefits. Data reflecting the likelihood of employment income could be based on data provided for ACH transactions posted to the account (e.g., ACH data indicating payroll deposits), or for non-ACH deposits (e.g., check deposits), based on the payor name or account, the check amount, or other check deposit information (e.g., by comparing that information to prior employment data provided by the beneficiary or by comparing that information to transaction patterns or history). In some embodiments, the periodicity or timing of deposit transactions might be relevant and could be evaluated.

An asset verification request, on the other hand, might be used by an entity (such as a mortgage company) to verify account balances. For example, a mortgage applicant may state that the applicant has sufficient funds saved in one or more accounts to make a down payment (or sufficient funds saved to supplement income as needed to make mortgage payments). In this example, a mortgage company needs to verify that balances in the applicant's accounts are adequate to meet the applicant's financial needs after the mortgage has been granted.

Embodiments of the present invention support alternative asset search and verification queries or requests. For example, systems and methods as described herein may be used in various situations where account information (such as balances) may be needed, such as to qualify or comply with certain government programs, to obtain consumer/commercial loans, or to initiate legal or other actions. These other situations include (but are not limited to) programs involving cash or noncash welfare payments, health care assistance, Supplemental Nutrition Assistance Program (SNAP), Supplemental Security Income (SSI), child support requests (e.g., confirming financial means or needs), Housing Subsidies, Earned Income Tax Credits (EITC), corporate audit verifications, small business loans, student loans, student financial assistance, credit checks, and delinquent tax collections.

Other embodiments may support asset search and verification requests for various kinds of accounts or account information beyond those maintained at financial institutions. For example, government agencies may contribute benefits data, including details relating to those benefits and relating to the beneficiary, such as name, address, social security number (SSN), date of birth, employer (if any), date benefits applied for, type or amount of benefits, date benefits began, agency or agency location, and so forth. As should be appreciated, such information (particularly when accessible by using a personal identifier or SSN of the beneficiary), can be used to identify and assess the risk of fraud when processing a beneficiary's request for benefits.

In addition, systems and methods of the present invention permit account information from a large number of banking and other institutions as well as from government agencies to be stored in a single database system so that accounts across all of those institutions or agencies may be searched or verified with one request. Not only does this eliminate the need for contacting multiple institutions and agencies, but it also permits the data from individual accounts (or multiple accounts) to be analyzed for risk-related factors (e.g., in the case of mortgage applications, factors indicating savings patterns, suspicious deposits, and possible links to known fraudsters/con artists; and in the case of government benefits, factors indicating suspicious transfers to third parties or benefits received across multiple jurisdictions or agencies). In some embodiments, search or verification requests may be batched and sent daily. In other embodiments, an individual search or verification request can be sent electronically (on-line and in real-time), and an immediate response can be returned by the system. In one implementation, the located account information sent in the response can be immediately reviewed, perhaps in the presence of the applicant (e.g., while a mortgage applicant is in the presence of a mortgage officer), thus permitting the applicant to explain discrepancies and provide further information that can be used to refine subsequent requests, if appropriate. Such an exchange of information in real time may significantly reduce the time and cost of mortgage qualification, cash and services benefits applications and other processes requiring a search or verification of accounts.

Turning now to FIG. 1, there is shown an exemplary system 100 for locating and accessing account information. The account information is stored and processed at a central account database system 110 having a database device 120 for storing account information and an account database management system (DBMS) 130 for managing the data in database 120 (e.g., the DBMS stores, retrieves, arranges, sorts and processes the data in the database). As illustrated, the data used to populate the database 120 is obtained from a number of financial institutions 140. In addition, requests to access the account data stored in database system 110 may be received from government agencies 150 (e.g., to establish qualification for benefits), from mortgage companies 160 (e.g., to verify account balances) and from other entities 170 (e.g., needing to locate and access account data for various reasons, such as creditworthiness, ability to supply funds, or debt or asset verification).

The financial institutions 140 maintain financial accounts, and include banks, savings and loan associations, investment firms and similar institutions. The accounts for which data is provided may include checking accounts, savings accounts, certificates of deposit, brokerage accounts, money market accounts, and other financial accounts (in the United States or elsewhere). Accounts may also include (i) reward or loyalty accounts providing merchant reward points, such as in the exemplary case of retail sales; (ii) online financial accounts such as PayPal accounts; (iii) online gaming accounts, such as Farmville or Second Life accounts; or (iv) frequent flyer programs or stored value accounts. Further, accounts may include credit or loan accounts, credit card accounts, debit accounts, prepaid accounts, or any account regarding any desired type of financial information.

It should be appreciated that, while the embodiment illustrated in FIG. 1 assumes financial institutions will contribute data, and that government agencies, mortgage companies and other entities will access the data, in some cases the financial institutions 140 may also access account data in system 110 (e.g., as part of a loan application) and government agencies 150, mortgage companies 160 and other entities 170 may contribute account data (e.g., benefits accounts and mortgage accounts). Thus, in their broadest sense, financial institutions 140 may represent any kind of institution or other entity maintaining an account or asset (financial or otherwise), and government agencies 150, mortgage companies 160 and other entities 170 may represent any kind of entity (governmental, commercial or otherwise) wanting to locate and/or verify accounts or assets that are maintained at various institutions.

FIG. 2 illustrates exemplary data provided to (and stored in) the database system 110 by each of the financial institutions 140. In this particular example, the data comprises account data for a bank account, and thus includes the following data fields (collectively designated as 202 in FIG. 2):

Routing and Transit Number (RTN) Account Number

Account Type (e.g., checking, savings, certificate of deposit, investment account)

Social Security Number (SSN)/Tax ID Number

Account Status (open/present, closed, deceased, non-sufficient funds, etc.)

Name of Account Holder(s) Authorized Signor(s) of Account Address(es) of Account Holder Email Address(es) of Account Holder Phone Number

Date of Birth (DOB) of Account holder Data date (date of receipt by system 110)

Current Balance

Average Balance (e.g., average balance over the past 30 days)

Interest Paid

Maturity Date (e.g., maturity date for a certificate of deposit)

As should be appreciated, FIG. 2 shows data for only one account, and in practice there would be many accounts from many institutions stored in database system 110.

As seen in FIG. 2, the data includes an initial transfer 210 for each of the data fields (current and historical information at the time of the initial transfer), and subsequent periodic transfers 212-1 through 212-n for most of the same data fields (to keep the data updated). In FIG. 2, the illustrated periodic data transfers 212-1 through 212-n are each transferred and stored daily (Day 1, Day 2, Day 3, etc., up to the current day). Such a frequent updating is generally preferred, although is some embodiments and applications a less frequent updating might be acceptable. The updated data fields are illustrated as including the same data as the initial transfer, other than the RTN, Account Number and Account Type fields, since it is assumed, for purposes of the described embodiment, that these three data fields will remain unchanged over the life of the account.

Also, FIG. 2 shows each updated daily transfer of data (212-1 through 212-n) having all fields 202 in database system 110 populated with data (other than RTN, Account Number and Account Type). However, in practice, much of that data will not change between transfers, and so database system 110 may be managed so that only the changed data in a daily transfer will be stored (in such case, especially if updates are daily, many of the data fields illustrated in FIG. 2 would in fact not be populated in order to efficiently manage storage space and minimize unnecessary data processing). This filtering of unnecessary data could be implemented in one embodiment by database system 110 being programmed to review data fields as they are received from the financial institutions 140 and to remove data that has not changed since the day before. In another embodiment, the financial institutions 140 may have systems on-site and programmed to remove unchanged data before it is transmitted.

It should be appreciated that, since the data stored in database system 110 is likely to be extensive for any given account, the account data could be processed in a number of ways by system 110, in addition to being available to a requester making an account search or verification request. For example, the data could be processed to provide balance information in various forms (e.g., a single, current 30 day average balance, or average balances over 6 months, over 1 year or longer). The needs of the requester can thus be met by processing data in a way that is useful to the requester (e.g., a governmental entity is likely to need different information than a mortgage company). In a response the data associated with any account can be filtered, processed and stored in a way to provide only the information on the account that is most useful to the requester.

In addition, and as will be described in more detailed later, the data associated with an account can be analyzed (and, in some cases, compared to data from other, external sources) to provide risk scores or other risk-related data pertinent to the request. For example, the database system 110 may respond to a mortgage company request with not only basic account information (current status, current account balance, and average balance), but also with alerts and flags if critical data has recently changed (new signers, new account holder names, significant changes in balances, etc.). Also, patterns for deposits and withdrawals (e.g., as reflected in daily balances) can indicate if the account holder is a consistently good saver, or has relied on a single or a few large deposits in order to reach the current balance. If the entity managing the database system 110 provides risk-related data, then data stored in the database could also include a risk marker 216 (stored in a “Risk Flag” field as seen in FIG. 2) that indicates risk factors have been identified for the account. The risk marker could be as simple as a “yes” or “no,” and in other embodiments could be a code to indicate whether the risk is relevant to specific categories of requesters, such a government benefits program, a mortgage company, a creditor, or some other request category. It should be appreciated that some factors (e.g., recent patterns of transfers out) would be relevant to a request from a government benefits program, and the same factors may have little or no relevance to a mortgage company. In embodiments where the system has collected risk-related data (in addition to the risk marker itself), such data could be stored in a separate table of data (to be described later), and would only be accessed if the risk is relevant to the purpose of the request.

FIGS. 3, 4 and 5 illustrate processes for responding to requests received at the database system 110. Before proceeding with descriptions of such Figures, it should be noted that a request to the system 110 may have a standard format and include information pertinent to the person (for whom the account data is sought), such as account holder SSN, name, address, and bank name(s) and account numbers (if any). However, information needed to identify any accounts for the person could be minimal and, in one embodiment, might only be an SSN. For example, in the case of an account search request (e.g., by a government agency doing a search for accounts), the SSN may be the only identifier provided and used to locate accounts. Other relevant data can be provided, if desired, to provide more accuracy and confirm matches (name, address, and even bank account numbers—if supplied by the person), and generally more information will be returned and its accuracy improved when more personal information is provided. In the case of an account verification request (e.g., by a mortgage company wanting to verify balance information supplied by an applicant), account numbers would typically be provided (for redundancy) as identifiers in addition to an SSN, to make sure that any account identified by an applicant is considered in verifying account balances. But even in that example, the system 110 could process and return account information based on a social security number. However, with either type of request, it should be appreciated that in some embodiments the requester may only provide a social security number as an identifier, and information can be returned by system 100 based only on that identifier and not relying on account numbers or other data concerning the account holder.

Turning now to FIG. 3, a request for an account search (e.g., locating for a government agency any account at any institution belonging to a person that is the subject of the search) is received by system 110 (step 310). The system determines if the request is valid (step 312). Such a determination could be based on several possible factors, such as whether the requester is authorized (e.g., the requester has, in advance, been properly authorized as an entity or individual), whether the request has been properly formatted (e.g., a personal identifier, such as a provided SSN, has the correct number of digits or is recognized as a valid SSN), and whether the device transmitting the request is recognized (e.g., from previous transactions or has been authorized in advance by the requester). If the request is not valid, the requester is notified (and the request is not processed further). If the request is valid, the system next determines whether there is an account in the database system 110 that matches the provided personal identifier (step 314). If the personal identifier does not identify any account, the requester is notified and the process ends (as indicated in FIG. 3). Alternatively, other steps can be taken (point “A” in the drawings) to identify accounts without using a social security number (such steps will be described shortly in conjunction with FIG. 4).

If accounts are identified with the provided personal identifier, the system looks for matches with other data (if any) provided by the requester (step 320). For example, a name or address provided in the request is compared to the data stored in system 110 for the identified account, and if there is no match the requester is notified and the search may end (at least temporarily). Alternatively, the process could continue, but with the understanding that the account data may not be relevant to the person that is the subject of the request. If the data matches at step 320, then the data for the identified account is retrieved, step 322. If risk data is also to be provided (if available and requested, step 324), then the risk data is retrieved (step 326) and the retrieved data is provided to the requester as part of the response (step 330).

As mentioned above, in some cases, even if an account is not identified with a personal identifier such as an SSN (step 314), the system 110 can be programmed to locate accounts using other personal information of the person in question. This is illustrated in FIG. 4, where the system 100 first looks for other matches of personal information (e.g., names, addresses, phone numbers) (step 410), and if there is match (step 412), the system may also analyze the match to verify that the information is for same account holder (step 414). As an example, this last step can be based on the amount of information matched, so that with two or more pieces of personal information being the same (both name and address for an account are the same as the name and address in the request) a match is indicated. In this example, if there is there is no match, the system 100 notifies the requester and the search ends. As an additional step, the system 100 may also further review any account where a match is made and verified at steps 412 and 414, identify the personal identifier such as an SSN for that verified account, and then also identify any other accounts in the database (at any institution) having the same personal identifier as the verified account (step 416). This process then returns to the process in FIG. 3, with any retrieved data provided back to the requester.

FIG. 5 illustrates a process similar to that of FIG. 3, but rather than an account search request, this process is used to respond to an account verification request (e.g., from a mortgage company). An account verification request is received by the system 110 (step 510) and the system determines if the request is valid (step 512). The system then determines if any accounts stored in the system are identified by the provided personal identifier such as an SSN, step 514. Since many account verification requests will also include account numbers provided by an applicant, the system determines if any accounts are identified by provided account numbers (step 516). The accounts that are identified (either at step 514 or step 516) are retrieved (step 522).

The system notifies the requester as to the nature of the matches (step 520). If there is no match of any accounts (no match of either the personal identifier or the account number), the requester is so notified and the process may end with that notification at step 520 (as indicated in FIG. 5). Alternatively, additional steps can be taken (point “A” in the drawings) to identify accounts (such additional steps are shown in, and were earlier described in conjunction with, FIG. 4). If, at step 520, there has been a match of only one of the personal identifier or account number, the requester is so notified (as to what identifier or information resulted in the match) and the process continues to the earlier described step 522 (account data for the identified account is retrieved).

If risk data is also to be provided (if available and requested, step 524), then the risk data is retrieved (step 526) and the retrieved data is provided to the requester as part of the response (step 530).

While FIGS. 3, 4 and 5 illustrate the search or verification process ending when no accounts are identified or found within system 110 (e.g., at steps 314, 412, and 520), it should be appreciated that other methods could be employed to respond to a search or verification request, in the event of an account not being found within system 110. For example, in one embodiment, when a requester provides account numbers and one or more of those account numbers are not found in the system 110, the system 110 could be configured to forward those account numbers to the institution(s) where they are maintained (e.g., using an RTN or bank name provided with the request), and then to respond to the requestor with any information supplied directly by the institution. In some cases, information supplied directly by the financial institution may supplement the account data retrieved from database 120 and, in those cases, both the information from the financial institution and account data retrieved from database may be provided in a response to the requestor (e.g., at steps 330 and 530). The methods just described could be accomplished automatically (on a batched basis or in real-time) in response an account number not being found in system 110 or, alternatively, could be accomplished with the assistance of personnel involved in operating system 110. In yet another embodiment, the system 110 could be electronically linked to the systems at various financial institutions 140 and configured to remotely search account databases at those institutions, so that as the system 110 searches its own database 120 it could likewise search (simultaneously or otherwise) the databases of the linked financial institutions and combine any located data in a response to a requester.

In some embodiments risk-related data (e.g., a risk score) may be generated based on the account data provided to and stored database system 110. This is illustrated by the scoring model and process of FIG. 6, where the account data for any given account is provided to scoring logic 610. The scoring logic, which could be implemented within the database management system 130 or a separate processing system (not shown) within central account database system 110, may use a statistical or rules-based analysis (other forms of analysis, such as artificial neural networks, could also be used) to develop a score (examples of analysis used by scoring logic 610 will be given shortly). In some instances, the account data may not be sufficient to generate a score (e.g., the account has recently been opened, or there has been very little or no account activity). In such case, the account data may be stored in a hold account queue 612 until sufficient data is available. In other cases, where there is sufficient data, the account data and resulting risk score may be stored in a scored account queue 614, which includes a risk score table 620.

The process of FIG. 6 also illustrates that the scoring process may be continuous. As additional new account data arrives for any accounts represented in the hold account queue 612, the account data is reapplied to the scoring logic 610. The additional data is also used in association with already scored accounts in scored account queue 614 to make fresh calculations of risk data for those accounts. That is, the scoring logic 610 is periodically re-run using updated account data (along with previous data in the scored account queue 614), and the table 620 is updated with new scores as they are generated. Over time, most of the accounts represented in the hold account queue 612 should migrate to the scored account queue 614. Eventually, most active accounts will have risk scores in table 620.

In FIG. 6, risk scores 622 in table 620 are illustrated as numerical (from 1 to 100), with “100” representing the highest risk and “1” representing the lowest. Of course other, simpler forms of risk data could be generated, such as only three risk levels (“low,” “medium,” and “high”). Also, risk reasons 624 are illustrated in table 620. Such reasons (or codes for such reasons) could be based on risk factors described below.

The following tables illustrate scoring analysis (exemplary risk factors and corresponding risk impact) that could be used in scoring logic 610, for both an account search request (involving government benefits) and an asset verification request (involving a mortgage application). In one embodiment, the risk scores could be calculated by initially assigning a neutral score (e.g., 50), and then increasing or decreasing the initial score based on the risk impact identified in the tables. Also, individual risk factors could be weighted differently, e.g., depending on desires of the requester or based on experiential data collected by the operator of the system 110. Further, some risk factors require comparing account data to relevant data in separate, external databases (as an example, such databases might store names, addresses, email addresses, phone numbers and account numbers of suspected fraudsters). The system 110 would access those external databases as necessary in performing various risk analysis steps.

Risk Score Analysis Account Search - Government Benefits Factors Risk Impact Transfer In/Out Patterns (money flow in and Frequent deposits and withdrawals - out of account) increased risk (likely attempt to keep balances low) Infrequent transactions - decreased risk Dates of Withdrawals (in relation to program Withdrawals within 6 months of begin date - requirements specifying a begin date for increased risk (likely attempt to conceal balances to be below program threshold assets) amount) Withdrawals more than 6 months prior to begin date - decreased risk Amount of Withdrawals (e.g. total At least one withdrawal - increased risk withdrawals of $1000 during past 5 years) No withdrawals - decreased risk Number/Nature of Located Accounts 5 or more located accounts (likely attempt to spread assets) - increased risk Less than 5 located accounts - decreased risk Accounts located but not identified by beneficiary - increased risk Names, addresses, phone numbers on account Matches with suspected fraudsters - (in addition to those of beneficiary) increased risk No matches with suspected fraudsters - decreased risk Account SSN/Name Match SSN or name for account do not match those provided in request - increased risk Both SSN and name for account match those provided in request - decreased risk

Risk Score Analysis Mortgage Application Factors Risk Impact Saving Pattern Infrequent deposits during each month (not a likely consistent “saver”) - increased risk Frequent and consistent deposits - decreased risk Added Signer Signer address same as applicant - decreased risk Signer address at zip code distant from applicant - increased risk Name or SSN of new signer matches suspected fraudsters - increased risk No matches with suspected fraudsters - decreased risk Recent deposits Large Amount(s) - increased risk Small amount(s) - decreased risk

Also, because the system 100 will likely store account information across most (if not all) financial institutions, additional data (not directly related to the account at hand) can be collected to provide additional forms of risk analysis. For example, if account data for an account is accessed and it reveals a large deposit (or a series of recent deposits that total a large amount), all other accounts in the system could be checked to see if a corresponding and identical withdrawal amount (or series of withdrawals) can be matched, thus linking another account (as a source account) to the account at hand. The system 110 could then check external databases to see if the source account is associated with a fraudster.

Embodiments of the invention also support other useful ways to tap the extensive and rich source of information maintained in the system 110. For example, the account data (including the risk scores) maintained in the system 110 may be used to assess creditworthiness. Not only could stored risk data be used in such an assessment, but loan or other credit accounts could be accessed (e.g., using only a SSN) to locate outstanding balances or credit limits (when stored in association with such accounts), and thus determine either the general creditworthiness of a person or entity (e.g., a person applying additional credit), but also verify representations made by an applicant in connection with the applicant's existing accounts.

As a further aspect of the present invention, a government or law enforcement agency may provide one or more personal identifier(s) corresponding to an individual or an entity named in a subpoena (or an instrument such as a National Security Letter or Writ of Execution) for financial or accounting records access, and the provided personal identifier(s) is/are used to determine which institutions, if any, have account or financial information for the individual or an entity named in the subpoena. If one or more of such institutions are found to have such account or financial information for the individual or an entity named in the subpoena, the names of the matching institutions are provided to the government or law enforcement agency with sufficient information (account number or identification information, for example) so that the subpoena may be efficiently served on the one or more matching institutions. If no matching institutions are found, indicia showing no match found may be returned to the government or law enforcement agency. As described more completely below, additional embodiments may perform analysis to provide additional information to the querying agency. The personal identifier for the individual or entity named in the subpoena may comprise any desired identification element, including, but not limited to, an SSN, a personal name, a mailing address, a physical address, the name of a corporate entity, a driver's license number, a prisoner number, an immigration number, a Matricula Consular number, or any other desired indicia. Further, personal identifiers may constitute a plurality of information designed to either narrow or broaden the search criteria depending on the desired result. Requiring more than one match for a plurality of provided identifiers might produce fewer results and would narrow the search. A match for any one of a plurality of provided identifiers might produce more results and would broaden the search.

For example, furnishing a plurality of personal identifiers such as an SSN and name and address (and requiring that an identified account have a match for each of the SSN, name and address) may further refine the search results and limit false positives, but depending on the amount of information returned, submissions of multiple identifiers, if a multiple match is required, could return too little information to be useful. Optionally, and to further refine results, the submitting agency may specify which of the submitted personal identifiers are required, and which may be optional, or which may be required in combination. For example, the submitting agency may specify that both a last name and an SSN must match the submission. In some embodiments, personal identifiers may comprise a list of related information for a suspect individual, for instance, a list of personal identifiers corresponding to known associates of the individual, and accounts of the known associates may be identified (along with the accounts of the suspect individual). Using additional analysis techniques, which may include link analysis or network analysis, account information corresponding to known associates and to others linked to the individual or entity identified in the subpoena may be returned to the submitting agency.

A simplified illustration of one such process is seen in FIG. 7. The process of FIG. 7 is similar to (and has steps corresponding to those of) of FIG. 3, but more specifically involves a search request (step 710) from a government agency for an individual or entity contemplated as the subject of a subpoena. As described in conjunction with FIG. 3, the system 110 determines whether the request is valid, step 712, and whether any accounts associated with a personal identifier of the subject (such as a social security number) can be identified, step 714. If there is no SSN match, then the requester is notified (and the process may end), but optionally, other steps can be undertaken to identify accounts without using a social security number (steps proceeding from point “A” in the drawings, using a process similar to that described earlier in conjunction with FIGS. 3 and 4). At step 720 other account data (e.g., name and address, if any, provided with the request) may be used to provide additional confirmation that the identified account is matched to the person that is the subject of the search. While not illustrated in FIG. 7, linking and network analysis can optionally be used to identify additional accounts and provide other information that may have some association with the subject of the contemplated subpoena, as will be described in connection with a specific example to follow shortly. Account data for any identified account is retrieved at step 722. As in FIG. 3, if risk data associated with an identified account is available (step 724), it may also be retrieved (step 726). Among other things, risk data may be used to determine the need for quickly executing a subpoena and then seizing an account that has a high risk of being involved in fraudulent activity (and that may be likely to have its balance quickly depleted/transferred by the fraudster/account holder). The retrieved data is provided (step 730), and a subpoena is prepared and executed at step 732 by the government agency.

As a specific example addressing an embodiment of the present invention, consider a hypothetical subpoena that is planned to be issued so that a law enforcement agency may find and obtain financial account information (and possibly related information) for an individual named Vito A. Corleone who has an SSN of 123-45-6789. Prior to embodiments of the present invention being available, difficulties immediately arise in trying to determine which financial institutions may have accounts for Vito Corleone; prior practices may have involved serving subpoenas or NSLs on a large number of financial institutions hoping that one or more of them have an account for Vito Corleone. In the process, much time and expense was wasted serving the subpoenas or NSLs to the institutions not having accounts for Vito, as well as the wasted time and expense borne by the financial accounts in responding to such “blind guess” subpoenas. However, in embodiments of the present invention, the law enforcement agencies may be provided indicia regarding which institutions have accounts related to Vito Corleone with a matching SSN, and optionally, account identifying information corresponding to accounts for which Vito is a signatory.

In a modification of the previous example, consider the case where no hits were found for Vito Corleone, with or without his SSN, at any institution's records stored in the database system (110) of the present invention. It may be likely that accounts may have been opened at various institutions by Vito's known associates to attempt to conceal Vito's financial transaction information. In an embodiment of the present invention, Vito's last known address was known by the submitting law enforcement agency (123 Genco Way, Long Island N.Y.), and a list of known associates: P. Clemenza, S. Tessio, L. Brasi, D. Tommasino, and T. Hagen. A query could then be submitted to systems of the present invention to find accounts matching his address and any of his known associates, and such accounts may then be scrutinized to determine whether they are associated with Vito Corleone. Those of skill in the relevant arts also realize that other cross-matching information (for example Vito's middle name “Andolini”) might be utilized with or without his SSN, and with or without other identifying information such as known associates. Further, through analyzing a network of Vito's associations created through linking and network analysis techniques as more completely described in U.S. Provisional Patent Application No. 61/448,156 filed Mar. 1, 2011 entitled, “System and Method for Suspect Entity Detection and Mitigation,” the disclosure of which is hereby fully incorporated by reference for all purposes, ancillary information regarding Vito Corleone's social or financial transaction history may be analyzed to determine possible accounts that have some association with Vito. Types of ancillary information provided about Vito may include checking account records of any kind (bank statements, cancelled checks, etc.), loan information (loan applications, ledgers, etc.), savings account and securities records (certificates of deposit, investments, etc.), records of any safe deposit boxes at a bank, supporting financial documents (copies of tax returns, credit reports, etc.), current or present addresses associated with an account, hot files, accounts closed for cause, mobile or land line phone numbers associated with Vito or his present or prior addresses, and the like. Once a network has been constructed with Vito's identifying information, related accounts (or other information) and the institutions that host them, may be provided to the querying law enforcement agency.

Submissions of requests for subpoena/NSL account identification may be made by the requesting agency individually in a real-time, or in a single or grouped batch mode submittal that is executed at a predetermined time interval (for example, overnight). Additionally, further analysis could produce information that may be provided to the requesting government or law enforcement agency regarding identity information for other individual signatories on joint accounts that correspond to the individual or entity named in the subpoena; prior transactions indicating financial fraud related to the individual or entity named in the subpoena, and through network analysis, identifications of or risk indicia regarding any potential fraud rings associated with the individual or entity that is named in the subpoena. As such, additional related investigatory leads may be provided to the government or law enforcement agency as a result of social or transactional associations with other entities. In an additional aspect, the requesting agency (or an entity, broker, or processor acting on the agency's behalf), after determining which institutions possess information about the subject of the subpoena/NSL, may send to the relevant institutions a formatted request for information that allows the possessing institutions to “fill in the blanks” for any missing data that is pertinent to the subject of the subpoena/NSL, and the requesting entity/broker/processor may process the response on the institution's behalf directly to the law enforcement agency. In a further aspect of the present invention, the requesting government agency may specify to a processor/broker the relevant laws, statutes, rules, or orders under which it has acting authority to submit the subpoena/NSL, and the processor/broker pursues obtaining the information for the agency on its behalf. Further, the processor/broker may utilize the specified listing of laws, statutes, rules or orders furnished by the government agency to tailor the information request to one or more institutions that have been determined to possess information about the subject of the subpoena/NSL, and may optionally filter or redact any information that is received from the relevant institutions that is not permitted to be provided under a legal framework of identified statutes, laws, or rules.

FIG. 8 is a block diagram illustrating an exemplary computer system upon which embodiments of the present invention may be implemented. This example illustrates a computer system 800 such as may be used, in whole, in part, or with various modifications, to provide the functions of the central database system 110, including the DBMS 130 and the scoring logic 610, as well as other components and functions of the invention described herein.

The computer system 800 is shown comprising hardware elements that may be electrically coupled via a bus 890. The hardware elements may include one or more central processing units 810, one or more input devices 820 (e.g., a mouse, a keyboard, etc.), and one or more output devices 830 (e.g., a display device, a printer, etc.). The computer system 800 may also include one or more storage devices 840, representing remote, local, fixed, and/or removable storage devices and storage media for temporarily and/or more permanently containing computer-readable information, and one or more storage media reader(s) 850 for accessing the storage device(s) 840. By way of example, storage device(s) 840 may be disk drives, optical storage devices, solid-state storage device such as a random access memory (“RAM”) and/or a read-only memory (“ROM”), which can be programmable, flash-updateable or the like.

The computer system 800 may additionally include a communications system 860 (e.g., a modem, a network card—wireless or wired, an infra-red communication device, a Bluetooth™ device, a near field communications (NFC) device, a cellular communication device, etc.) The communications system 860 may permit data to be exchanged with a network, system, computer, mobile device and/or other component as described earlier. The system 800 also includes working memory 880, which may include RAM and ROM devices as described above. In some embodiments, the computer system 800 may also include a processing acceleration unit 870, which can include a digital signal processor, a special-purpose processor and/or the like.

The computer system 800 may also comprise software elements, shown as being located within a working memory 880, including an operating system 884 and/or other code 888. Software code 888 may be used for implementing functions of various elements of the architecture as described herein. For example, software stored on and/or executed by a computer system, such as system 800, can be used in implementing the processes seen in FIGS. 3-7.

It should be appreciated that alternative embodiments of a computer system 800 may have numerous variations from that described above. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Furthermore, there may be connection to other computing devices such as network input/output and data acquisition devices (not shown).

In other aspects, embodiments of the invention may be used in a context involving a third party, for example for quality control, auditing, or other purposes. In particular, embodiments of the invention may facilitate the securitization and secondary marketing of home mortgages by a government sponsored enterprise such as the Federal National Mortgage Association (FNMA) (also known as “Fannie Mae”) or the Federal Home Loan Mortgage Corporation (FHLMC) (also known as “Freddie Mac”).

FIG. 9 illustrates relationships between various parties involved in such a scenario. In the example of FIG. 9, a loan originator 901 receives a mortgage application from a borrower 902. The application includes, among other information, personally identifying information (PII) identifying the borrower. The PII may be, for example, a social security number, a tax ID number, or another recognized piece of information identifying borrower 902. The mortgage application may also include statements of the borrower's assets and liabilities, income, expenses, and the like.

Loan originator 901 typically may make its decision as to whether to issue the loan based on the perceived risk of the proposed loan, in light of the financial situation of borrower 902. As such, loan originator 901 may wish to verify the statements made by borrower 902 in the application, to the extent possible.

For this purpose, loan originator 901 may provide the PII of borrower 902 to asset location/verification service provider 903. Provider 903 may utilize a database system such as database system 110 described above to automatically locate or verify assets of borrower 902, based on the received PII. For example, provider 903 may maintain account database 120 holding account records from a number of financial institutions 140. Provider 903 locates accounts associated with borrower 102, and returns a report of its findings to loan originator 901.

Provider 903 may use any one, any combination, or all of the techniques described above or other techniques in researching the financial status of borrower 902. For example, provider 903 may locate accounts owned by borrower 902 and report the current balances in those accounts, so that loan originator 901 can gain confidence that borrower 902 has correctly stated its financial condition. In addition, provider 903 may investigate transaction data involving accounts owned or associated with borrower 902, to infer other information about borrower 902.

For example, database 120 may include records of deposits and withdrawals from accounts owned by borrower 902. The deposit and withdrawal data may be investigated to look for patterns that appear to increase or decrease the risk of making a loan to borrower 902.

In some embodiments, provider 903 investigates the pattern of deposits made to accounts held by borrower 902, for example to see if the balances in one or more of the borrower's accounts are due to a consistent pattern of similarly-sized deposits, or whether one or more balances were achieved in part by one or a few large deposits made within a predetermined time period. The relative size of a deposit may be measured in any workable way, for example in relation to the average deposit made to an account, in relation to the average balance in the account, or in another way.

In one embodiment, the relative size of deposits may be evaluated according to one or both of the following formulas:

$\begin{matrix} {{{relative}\mspace{14mu} {deposit}\mspace{14mu} {size}} = \frac{{Current}\mspace{14mu} {deposit}\mspace{14mu} {amount}}{{Average}\mspace{14mu} {deposit}\mspace{14mu} {amount}\mspace{14mu} {in}\mspace{14mu} {past}\mspace{14mu} 90\mspace{14mu} {days}}} & \left. a \right) \\ {{{relative}\mspace{14mu} {deposit}\mspace{14mu} {size}} = \frac{{Current}\mspace{14mu} {deposit}\mspace{14mu} {amount}}{{Average}\mspace{14mu} {daily}\mspace{14mu} {balance}\mspace{14mu} {during}\mspace{14mu} {past}\mspace{14mu} 90\mspace{14mu} {days}}} & \left. b \right) \end{matrix}$

In formula a) above, the amount each deposit into an account is compared with the average deposit amount made into the account during a particular time period. In the example above, the time period is the most recent 90 days, but other time periods may be used as well. The threshold for considering a deposit to be large may be selected as desired, for example by loan originator 901. In some embodiments, a deposit may be considered large if it is at least 1.5, 2, 3, 4, 5, 10, or another number of times the size of the average deposit to the account during the time period of interest.

In formula b) above, the amount of each deposit into an account is compared with average daily balance in the account during a particular time period, for example 90 days or another suitable time period. The threshold for considering a deposit to be large may be selected as desired. In some embodiments, a deposit may be considered large if it is at least 0.5, 0.75, 1, 1.5, 2, 3, 4, 5, 10, or another number of times the average daily balance in the account during the time period of interest.

In some embodiments, either or both of these formulas may be used. For example, a deposit may be considered large only if it is at least twice the size of the average deposit made in the past 90 days, and is at least twice the average daily balance in the account over the past 90 days. Other formulas or criteria for recognizing large deposits may be used as well, in addition to, instead of, or in combination with formulas a) and b) above.

The report prepared by provider 903 preferably includes information about the deposit history of borrower 902. If no large deposits into a particular account are found, then the balance in the account may be deemed to have been achieved at least in part by a consistent pattern of deposits.

Presuming that loan originator 901 decides to proceed with the loan, the loan is closed. Loan originator 901 informs government sponsored enterprise (GSE) 904 that the loan has been made, including an identifier of the report that loan originator 901 received from provider 903, although the report itself is not included. GSE 904 may be, for example, and entity such as Fannie Mae or Freddie Mac, which may buy and securitize the loan. That is, GSE 904 may sell securities backed by a portfolio of loans including the loan made to borrower 902.

In order to evaluate the quality of the loan portfolio, GSE 904 may wish to review the information that loan originator 901 used in deciding to make the loan. GSE 904 requests from provider 903 the information in the asset location report that provider 903 made to loan originator 901 before the loan was closed. Because loan originator 901 gave the report identifier to GSE 904, GSE 904 can simply request the report by its identifier from provider 903. And because GSE 904 receives the report information directly from provider 903, the report provides an independent check on the practices of loan originator 901. The request from GSE 904 may typically occur some time after the closing of the loan, for example several months or more.

Provider 903 may perform other kinds of analysis as well. For example, the records in database 120 preferably include records of all deposits into the accounts held by borrower 902 (and other persons). Provider 903 may recognize a sequence of regular deposits made into an account of borrower 902, and may recognize that the deposits in the sequence are likely payroll deposits. For example, a sequence of deposits of the same or nearly the same amount may occur weekly or semi-monthly. The presumption that the sequence represents payroll deposits may be strengthened if the deposits are made by direct deposit from an identifiable company or organization that would have employees.

From this recognized sequence of deposits, provider 903 may be able to infer that borrower 902 is employed, and may also be able to estimate the employment income of borrower 902. For example, the amount of the deposit sequence may be annualized and adjusted for the likely effect of payroll tax and benefit withholding, to arrive at an estimate of the annual income of borrower 902. The income estimate may be included in the report produced by provider 903.

And because database 120 preferably contains records from a number of accounts at a number of financial institutions, additional detail may be available enabling a more accurate estimate of the income of borrower 902. For example, if another sequence of equal-size deposits to another account is found occurring on the same days as the presumed payroll deposits, this may indicate automatically-withheld savings being deposited to a different account than the bulk of the paycheck of borrower 902. The savings deposits may be detected even if the savings account is at a different financial institution than the primary account of borrower 902. If such a savings stream is found, the income estimate for borrower 902 may be adjusted accordingly.

In some embodiments, database 120 may also include information identifying the source of ACH or other automated deposits into the accounts covered by database 120. This information, combined with the identification of presumed payroll deposits as described above, may enable provider 903 to identify a presumed employer of borrower 902, and the presumed employer identification may be include in the report produced by provider 903. If borrower 902 listed its employer in the loan application, then the analysis by provider 903 may serve as a verification of the borrower's indication.

Database 120 may further contain records of withdrawals from accounts located using the PII of borrower 902, and these withdrawal records may be analyzed for additional information. For example, provider 903 may be able to identify a regular sequence of recurring automated withdrawals in a fixed amount and occurring on the same day of each month. Provider 903 may identify such a sequence as likely mortgage or other housing payments, auto loan payments, or other fixed expenses.

Database 120 may further contain non-transaction information contributed from various sources that may reflect on the risk associated with a loan. For example, banks or other financial institutions may inform provider 903 of past instances of fraud or abusive activity involving particular persons or accounts. Other sources of negative contributed information may include public arrest records, news reports of financial crimes, fraudulent activity such as marketing of stolen identification information conducted on the “dark” web, and other sources. The report produced by provider 903 may list such negative contributed information, or may note the lack of any negative contributed information on file associated with a particular person. Because database 120 preferably includes information submitted by a number of financial institutions, negative contributed information from one financial institution may inform a loan approval decision being made by another institution.

In some embodiments, the account records in database 120 may indicate that certain located accounts are joint accounts. Provider 903 may include in the report it generates an indication of joint account ownership. The report may include estimates of employment and income for joint account holders as well, and may include any negative contributed information found relating to any joint account holders.

FIG. 10 is a flow diagram illustrating steps performed according to some embodiments of the invention. In step 1001, an applicant, for example borrower 902, applies for a home mortgage from an originating financial institution (OFI) such as OFI 901. In step 1002, originating financial institution 901 obtains personal identifying information (PII) about the applicant. For example, the applicant may list a social security number or other identifying information in the mortgage application. In step 1003, originating financial institution 901 sends the personal identifying information about the applicant to an asset location/verification service provider such as provider 903. In step 1004, the location/verification provider locates assets of the applicant and may perform additional analyses of account data stored in a database such as database 120. Additional details of some embodiments of step 1004 are shown in FIG. 11.

In step 1005, the location/verification service provider sends the report and its identifier to the originating financial institution. The location/verification service provider also stores the report and its identifier for later access. In step 1006, the originating financial institution sends the report identifier to another party such as government sponsored enterprise (GSE) 904. The report itself is preferably not sent to the GSE or other party at this time. In step 1007, the loan is approved. (It is presumed for ease of explanation that the loan is approved. Of course, not all loans will be approved.) In addition, the loan may be sold to the GSE.

In step 1008, the location/verification service provider receives a request for the report information from the GSE or other party. The request includes the report identifier. In step 1009, the report information is communicated to the GSE or other party.

FIG. 11 is a flow diagram illustrating steps performed according to some embodiments by the location/verification service provider, for example within step 1004 of FIG. 10. In step 1101, provider 903 generates an identifier of the report to be prepared. In step 1102, provider 903 searches the database for accounts associated with the person identified by the personal identifying information received in the request, to locate accounts owned or otherwise associated with the identified person. In step 1103, account balances of the located accounts are retrieved. Other information may be received as well, including transaction data listing deposits and withdrawals flowing into and out of the accounts.

In step 1104, a pattern of deposits is analyzed, so that information about the deposit pattern can be included in the report if desired. In step 1105, provider 903 estimates the income of the identified person, based on the transaction data of the located accounts. In step 1106, provider 903 identifies a suspected employer of the identified person. In step 1107, provider 903 characterizes recurring expenses of the identified person, based on transaction data of the located accounts. In step 1108, provider 903 searches for negative contributed information about the identified person. In step 1109, the report is prepared.

The report may include any or all of the items retrieved, estimated, or deduced in steps 1102-1108. It will be recognized that not all embodiments may perform all of the steps of FIG. 11, and that different embodiments will produce reports with differing levels of detail. Other steps may be performed in some embodiments.

While embodiments of the invention have been described above in the context of securitization of home mortgages, in which a GSE requests during the securitization phase information from a report that was generated during the loan qualification phase, it will be recognized that other kinds of entities may request previously-prepared reports. For example, an auditor, an internal quality control department, or another kind of entity may request previously-prepared reports.

While various methods and processes described herein may be described with respect to particular structural and/or functional components for ease of description, methods of the invention are not limited to any particular structural and/or functional architecture but instead can be implemented on any suitable hardware, firmware, and/or software configuration. Similarly, while various functionalities are ascribed to certain individual system components, unless the context dictates otherwise, this functionality can be distributed or combined among various other system components in accordance with different embodiments of the invention. As one example, the central account database system 110 system may be implemented by a single system having one or more storage device and processing elements. As another example, the central account database system 110 system may be implemented by plural systems, with their respective functions distributed across different systems either in one location or across a plurality of linked locations.

Moreover, while the various flows and processes described herein (e.g., those illustrated in FIGS. 3-7, 10, and 11) are described in a particular order for ease of description, unless the context dictates otherwise, various procedures may be reordered, added, and/or omitted in accordance with various embodiments of the invention. Moreover, the procedures described with respect to one method or process may be incorporated within other described methods or processes; likewise, system components described according to a particular structural architecture and/or with respect to one system may be organized in alternative structural architectures and/or incorporated within other described systems. Hence, while various embodiments may be described with (or without) certain features for ease of description and to illustrate exemplary features, the various components and/or features described herein with respect to a particular embodiment can be substituted, added, and/or subtracted to provide other embodiments, unless the context dictates otherwise. Consequently, although the invention has been described with respect to exemplary embodiments, it will be appreciated that the invention is intended to cover all modifications and equivalents within the scope of the following claims. 

What is claimed is:
 1. A system, comprising: a database storing data for accounts from a plurality of institutions, the stored data for each respective account comprising at least a personal identifier for an account holder of that respective account; and a processor configured to: receive a request to locate assets, the request including a submitted personal identifier; automatically locate one or more accounts by matching the submitted personal identifier to a personal identifier stored in the database for the located accounts; retrieve from the database stored data associated with the located accounts; produce a report, the report indicating the assets contained in the one or more located accounts, the report also indicating a pattern of deposits into at least one of the located accounts; and provide the report to an entity from which the request to locate assets was received.
 2. The system of claim 1, wherein the report indicates that a balance in at least one of the located accounts was achieved in part by one or a few large deposits made within a predetermined time period.
 3. The system of claim 1, wherein the entity from which the request to locate assets is a first requesting entity, and the processor is further configured to: receive, from a second requesting entity at a time later than the production of the report, a request for information contained in the report, the request including an identifier of the report; and provide information contained in the report to the second requesting entity.
 4. The system of claim 3, wherein the second requesting entity is a government sponsored enterprise.
 5. A computer-implemented method, comprising: providing a database; storing, in the database, account data for accounts maintained at a plurality of institutions, the account data for each respective account comprising at least a personal identifier for an account holder of that respective account; receiving a request to locate assets, the request including a submitted personal identifier; automatically locating one or more accounts by matching the submitted personal identifier to the personal identifier stored in the database for the located accounts; retrieving at least some of the account data for the located accounts; producing a report, the report indicating the assets contained in the one or more located accounts, and the report indicating a pattern of deposits into at least one of the located accounts; and providing the report to an entity from which the request to locate assets was received.
 6. The method of claim 5, wherein the report indicates that a balance in at least one of the located accounts was achieved in part by a consistent pattern of deposits.
 7. The method of claim 5, wherein the report indicates that a balance in at least one of the located accounts was achieved in part by one or a few large deposits made within a predetermined time period.
 8. The method of claim 5, wherein the entity from which the request to locate assets was received is a first requesting entity, the method further comprising: receiving, from a second requesting entity at a time later than producing the report, a request for information contained in the report, the request including an identifier of the report; and providing information contained in the report to the second requesting entity.
 9. The method of claim 8, wherein the second requesting entity is a government sponsored enterprise.
 10. The method of claim 5, further including: ascertaining that one or more of the located accounts are jointly held; and indicating in the report which accounts are jointly held.
 11. A system, comprising: a database storing data for accounts from a plurality of institutions, the stored data for each respective account comprising at least a personal identifier for an account holder of that respective account; and a processor configured to: receive from a first requesting entity a request to locate assets, the request including a submitted personal identifier; automatically locate one or more accounts by matching the submitted personal identifier to a personal identifier stored in the database for the located accounts; retrieve from the database stored data associated with the located accounts; produce a report, the report indicating the assets contained in the one or more located accounts; provide the report to the first requesting entity; receive, from a second requesting entity at a time later than the production of the report, a request for information contained in the report, the request including an identifier of the report; and provide information contained in the report to the second requesting entity.
 12. The system of claim 11, wherein the second requesting entity is a government sponsored enterprise.
 13. The system of claim 11, wherein the report indicates that a balance in at least one of the located accounts was achieved in part by a consistent pattern of deposits.
 14. The system of claim 11, wherein the report indicates that a balance in at least one of the located accounts was achieved in part by one or a few large deposits made within a predetermined time period.
 15. The system of claim 11, wherein the processor is further configured to: identify a sequence of recurring deposits drawn from a common source and made to at least one of the located accounts over a period of time; identify from the identity of the common source a suspected employer of a holder of the at least one located account; and include in the report an indication of the suspected employer of the holder of the at least one located account.
 16. The system of claim 11, wherein the processor is further configured to: identify a sequence of recurring withdrawals from at least one of the located accounts over a period of time; estimate from the sequence of recurring withdrawals a recurring liability of a holder of the at least one located account; and include in the report the estimate of the recurring liability of the holder of the at least one located account.
 17. The system of claim 11, wherein the database includes negative contributed information received from a plurality of financial institutions about a number of account holders, and wherein the processor is further configured to: retrieve from the database at least some of the negative contributed information associated with the personal identifier received in the request to locate assets; and include in the report at least some of the negative contributed information.
 18. The system of claim 11, wherein the database includes negative contributed information received from a plurality of financial institutions about a number of account holders, and wherein the processor is further configured to: search within the database for negative contributed information associated with the personal identifier received in the request to locate assets; recognize that the database does not contain any negative contributed information associated with the personal identifier received in the request to locate assets; and include in the report the fact that the database does not contain any negative contributed information associated with the personal identifier received in the request to locate assets.
 19. The system of claim 11, wherein the processor is further configured to ascertain that one or more of the located accounts are jointly held, and to indicate in the report which accounts are jointly held. 